📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

**/*.{md,rst,html,txt}: Always spell NVIDIA in all caps. Do not use Nvidia, nvidia, nVidia, nVIDIA, or NV.
Use an NVIDIA before a noun because the name starts with an 'en' sound.
Do not add a registered trademark symbol after NVIDIA when referring to the company.
Use trademark symbols with product names only when the document type or legal guidance requires them.
Verify official capitalization, spacing, and hyphenation for product names.
Precede NVIDIA product names with NVIDIA on first mention when it is natural and accurate.
Do not rewrite product names for grammar or title-case rules.
Preserve third-party product names according to the owner's spelling.
Include the company name and full model qualifier on first use when it helps identify the model.
Preserve the official capitalization and punctuation of model names.
Use shorter family names only after the full name is established.
Spell out a term on first use and put the acronym in parentheses unless the acronym is widely understood by the intended audience.
Use the acronym on later mentions after it has been defined.
For long documents, reintroduce the full term if readers might lose context.
Form plurals of acronyms with s, not an apostrophe, such as GPUs.
In headings, common acronyms can remain abbreviated. Spell out the term in the first or second sentence of the body.
Common terms such as CPU, GPU, PC, API, and UI usually do not need to be spelled out for developer audiences.

Files:

• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

Link the first mention of a product name when the destination helps the reader.

Files:

• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

Spell NVIDIA in all caps. Do not use Nvidia, nvidia, or NV.

Files:

• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

**/*.{md,rst}: Format commands, code elements, expressions, package names, file names, and paths as inline code.
Use descriptive link text. Avoid raw URLs and weak anchors such as "here" or "read more."
Use title case consistently for technical documentation headings.
Introduce code blocks, lists, tables, and images with complete sentences.
Write procedures as imperative steps. Keep steps parallel and split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English.
Use can for possibility and reserve may for permission.
Use after for temporal relationships instead of once.
Prefer refer to over see when the wording points readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical docs.
Spell out months in body text, avoid ordinal dates, and use clear time zones.
Spell out whole numbers from zero through nine unless they are technical values, parameters, versions, or UI values.
Use numerals for 10 or greater and include commas in thousands.
Do not add trademark symbols to learning-oriented docs unless the source, platform, or legal guidance explicitly requires them.

Files:

• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-technical-docs.md)

**/*.md: Use title case consistently in technical documentation headings
Avoid quotation marks, ampersands, and exclamation marks in headings
Keep product, event, research, and whitepaper names in their official title case
Use title case for table headers
Do not force social-media sentence case into technical docs
Format code elements, commands, parameters, package names, and expressions in monospace
Format directories, file names, and paths in monospace using backticks
Use angle brackets inside monospace for variables inside paths, such as /home/<username>/.login
Format error messages and strings in quotation marks, keeping literal code strings in code formatting when clearer
Format UI buttons, menus, fields, and labels in bold
Use angle brackets between UI labels for menu paths, such as File > Save As
Use italics for new terms on first use, sparingly and only when introducing the term
Use italics for publication titles
Format keyboard shortcuts in plain text, such as Press Ctrl+Alt+Delete
Use owner/repo link text for GitHub repositories, preferring [NVIDIA/NeMo](link) over prose references like 'the GitHub repo'
Introduce every code block with a complete sentence
Do not make a code block complete the grammar of the previous sentence
Do not continue a sentence after a code block
Use syntax highlighting when the format supports it for code blocks
Avoid the word 'snippet' unless the surrounding docs already use it as a term of art
Keep inline method, function, and class references consistent with nearby docs, omitting empty parentheses for prose readability when no call is shown
Use descriptive anchor text that matches the destination title when possible for links
Avoid raw URLs in running text
Avoid generic anchor text such as 'here,' 'this page,' and 'read more'
Include acronyms in link text when a linked term includes an acronym
Do not link long sentences or multiple sentences
Avoid links that pull readers away from a procedure unless the link is a p...

Files:

• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (AGENTS.md)

SKILL.md files are skill entrypoints and must start with YAML frontmatter containing at least name and description.

Files:

• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

⚙️ CodeRabbit configuration file

**/SKILL.md: Do not flag SKILL.md files for missing SPDX headers. Skill entrypoints intentionally start with YAML frontmatter instead.
Verify that every SKILL.md keeps valid YAML frontmatter with at least name and description fields before the Markdown body.

Files:

• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (AGENTS.md)

Update README.md, fern/, package READMEs, and binding-support notes when public behavior, package names, examples, or supported bindings change.

**/*.{md,mdx}: Prefer the documented public API, not internal shortcuts
Keep package names, repo references, and build commands current
Keep release-process and release-notes guidance in repo-maintainer docs such as RELEASING.md, not as user-facing docs pages or CHANGELOG.md
Keep stable user-facing wrappers at scripts/ root in docs and examples; only point at namespaced helper paths when documenting internal maintenance work
When detailed dynamic plugin guides exist, keep Rust native plugin examples, Python worker plugin examples, and grpc-v1 protocol details on separate pages

If links in documentation change, run just docs-linkcheck.

Files:

• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-setup-observability/SKILL.md
• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Add the SPDX license header to all Markdown/MDX documentation files using the HTML comment block form.

Files:

• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-setup-observability/SKILL.md
• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

**/*: Format changed files with the language-native formatter before the final lint/test pass.
If dynamic plugin behavior changed, use maintain-dynamic-plugins and include the native SDK, worker protocol, Python SDK, docs, packaging, and Codecov surfaces in the validation plan.
If code changes alter APIs, bindings, commands, paths, packaging behavior, observability/adaptive semantics, or documented best practices, update any dependent maintainer or consumer skills in the same branch.
During iteration, prefer uv run pre-commit run --files <changed files...>.
Before review or handoff, run uv run pre-commit run --all-files.

Files:

• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-setup-observability/SKILL.md
• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

⚙️ CodeRabbit configuration file

**:

AGENTS.md

This file provides guidance to agents, including Claude Code and OpenAI Codex, when working in this repository.

Project Overview

NeMo Relay is a multi-language agent runtime framework for execution scopes, lifecycle events, middleware, plugins, and observability around tool and LLM calls. The core runtime is Rust. Primary supported bindings are Rust, Python, and Node.js. Go and the raw C FFI are experimental and source-first.

The shared runtime model is:

1. Scope stacks decide where work belongs and which scope-local behavior is visible.
2. Middleware registries decide what guardrails and intercepts run around managed calls.
3. Plugins install reusable runtime behavior from configuration.
4. Events record runtime behavior in ATOF form.
5. Subscribers and exporters consume events in-process or export them to ATIF, OpenTelemetry, OpenInference, or other backends.

Repository Structure

The repository layout separates the Rust runtime, language bindings,
documentation, integrations, and agent-facing skills.

crates/
  core/       # Rust core runtime crate, published as nemo-relay
  adaptive/   # Adaptive runtime primitives and plugin components
  python/     # PyO3 native extension for the Python package
  ffi/        # Raw C ABI layer used by downstream bindings such as Go
  node/       # NAPI Node.js binding and JavaScript/TypeScript entry points
python/
  nemo_relay/  # Python wrapper package: scopes, tools, LLM, middleware, typed helpers, plugins, adaptive helpers
  tests/      # Python tests
go/
  nemo_relay/  # Experimental Go CGo binding and tests
fern/         # Fern documentation site
scripts/      # Stable wrappers and helper scripts; build/test/docs entry points live in justfile
skills/       # Published Codex/agent skills for NeMo Relay usage patterns

Prerequisites

Insta...

Files:

• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-setup-observability/SKILL.md
• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/SKILL.md)

MDX top-of-file SPDX comments must use {/* ... */} delimiters instead of HTML comment delimiters (Must-Fix)

In MDX files, top-of-file comments must use JSX comment delimiters ({/* to open and */} to close); do not use HTML comments for MDX SPDX headers

Files:

• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update docs and examples.

Files:

• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If documentation examples or commands under docs/ change, run the targeted docs checks appropriate to the change.

Files:

• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx

⚙️ CodeRabbit configuration file

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}: Review documentation for technical accuracy against the current API, command correctness, and consistency across language bindings.
Flag stale examples, missing SPDX headers where required, and instructions that no longer match CI or pre-commit behavior.

Files:

• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

**/*.rs: Any Rust change must run just test-rust
Any Rust change must run cargo fmt --all
Any Rust change must run cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all for all FFI work since it is Rust work
Run just test-rust to validate FFI changes
Run cargo clippy --workspace --all-targets -- -D warnings to enforce strict linting on FFI work

When Rust files changed as part of Go work, also run cargo fmt --all, just test-rust, and cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all when Rust files are changed as part of Node work
Run cargo clippy --workspace --all-targets -- -D warnings when Rust files are changed as part of Node work
Run just test-rust when Rust files are changed as part of Node work

When changing the core Rust runtime or Rust-facing API surface, format Rust code with cargo fmt (rustfmt defaults), keep cargo clippy -- -D warnings clean, and satisfy cargo deny check per deny.toml.

**/*.rs: If any Rust code changed, always run just test-rust.
If any Rust code changed, also run cargo fmt --all.
If any Rust code changed, also run cargo clippy --workspace --all-targets -- -D warnings.
For Rust changes headed for review, run cargo fmt --all and cargo clippy --workspace --all-targets -- -D warnings even if relying on pre-commit.

Files:

• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

Changes to crates/core or crates/adaptive must run the full language matrix

Files:

• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/test-go-binding/SKILL.md)

If the change touched crates/core or shared runtime semantics, also use validate-change for broader validation

Files:

• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (AGENTS.md)

Follow binding naming conventions in Rust and Python: use snake_case.

Files:

• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (AGENTS.md)

**/*.{rs,py,js,mjs,cjs,ts,tsx}: Use Json = serde_json::Value in Rust-facing runtime APIs where the existing code expects JSON payloads.
Use Result<T> with FlowError in core runtime paths, and keep errors explicit and binding-appropriate at the wrapper layer.
Keep async behavior on the existing tokio-based model; bindings should preserve callback and future lifetimes rather than blocking or hiding async work unexpectedly.

Files:

• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Use language-appropriate naming conventions: Rust snake_case, C FFI exports prefixed nemo_relay_, Go PascalCase, Node.js camelCase, and Python snake_case.

Files:

• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Add the SPDX license header to all Rust, Go, JavaScript, and TypeScript source files using the corresponding // comment form.

Files:

• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If crates/core or crates/adaptive changed, run the full validation matrix across Rust, Python, Go, and Node.js.

Files:

• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If a language surface changed, always run that language's test target even when Rust core did not change.

Files:

• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

⚙️ CodeRabbit configuration file

crates/{core,adaptive}/**/*.rs: Review the Rust runtime for async correctness, scope isolation, middleware ordering, and event lifecycle regressions.
Pay close attention to task-local/thread-local scope propagation, callback lifetimes, stream finalization, and root_uuid isolation.
Public API changes should preserve existing behavior unless tests and docs show the intended migration path.

Files:

• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

⚙️ CodeRabbit configuration file

{crates/**/tests/**,python/tests/**,go/nemo_relay/**/*_test.go}: Tests should cover the behavior promised by the changed API surface, including error paths and cross-request isolation where relevant.
Prefer assertions on lifecycle events, scope stacks, middleware ordering, and binding parity over shallow smoke tests.

Files:

• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/add-middleware/SKILL.md)

Wire the new middleware chain into the execute path in crates/core/src/api/tool.rs or crates/core/src/api/llm.rs at the appropriate pipeline stage

Files:

• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/add-binding-feature/SKILL.md)

Implement the new or changed public runtime behavior first in the Rust core, especially under crates/core/src/api/ and related core modules such as crates/core/src/api/runtime/, crates/core/src/codec/, and crates/core/src/json.rs.

Files:

• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/maintain-dynamic-plugins/SKILL.md)

Do not add tests under src; Rust tests belong in crate tests/ trees, and Python SDK tests belong under python/tests.

Files:

• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

**/*.{md,rst,html,txt}: Always spell NVIDIA in all caps. Do not use Nvidia, nvidia, nVidia, nVIDIA, or NV.
Use an NVIDIA before a noun because the name starts with an 'en' sound.
Do not add a registered trademark symbol after NVIDIA when referring to the company.
Use trademark symbols with product names only when the document type or legal guidance requires them.
Verify official capitalization, spacing, and hyphenation for product names.
Precede NVIDIA product names with NVIDIA on first mention when it is natural and accurate.
Do not rewrite product names for grammar or title-case rules.
Preserve third-party product names according to the owner's spelling.
Include the company name and full model qualifier on first use when it helps identify the model.
Preserve the official capitalization and punctuation of model names.
Use shorter family names only after the full name is established.
Spell out a term on first use and put the acronym in parentheses unless the acronym is widely understood by the intended audience.
Use the acronym on later mentions after it has been defined.
For long documents, reintroduce the full term if readers might lose context.
Form plurals of acronyms with s, not an apostrophe, such as GPUs.
In headings, common acronyms can remain abbreviated. Spell out the term in the first or second sentence of the body.
Common terms such as CPU, GPU, PC, API, and UI usually do not need to be spelled out for developer audiences.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

Link the first mention of a product name when the destination helps the reader.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

Spell NVIDIA in all caps. Do not use Nvidia, nvidia, or NV.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

**/*.{md,rst}: Format commands, code elements, expressions, package names, file names, and paths as inline code.
Use descriptive link text. Avoid raw URLs and weak anchors such as "here" or "read more."
Use title case consistently for technical documentation headings.
Introduce code blocks, lists, tables, and images with complete sentences.
Write procedures as imperative steps. Keep steps parallel and split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English.
Use can for possibility and reserve may for permission.
Use after for temporal relationships instead of once.
Prefer refer to over see when the wording points readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical docs.
Spell out months in body text, avoid ordinal dates, and use clear time zones.
Spell out whole numbers from zero through nine unless they are technical values, parameters, versions, or UI values.
Use numerals for 10 or greater and include commas in thousands.
Do not add trademark symbols to learning-oriented docs unless the source, platform, or legal guidance explicitly requires them.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-technical-docs.md)

**/*.md: Use title case consistently in technical documentation headings
Avoid quotation marks, ampersands, and exclamation marks in headings
Keep product, event, research, and whitepaper names in their official title case
Use title case for table headers
Do not force social-media sentence case into technical docs
Format code elements, commands, parameters, package names, and expressions in monospace
Format directories, file names, and paths in monospace using backticks
Use angle brackets inside monospace for variables inside paths, such as /home/<username>/.login
Format error messages and strings in quotation marks, keeping literal code strings in code formatting when clearer
Format UI buttons, menus, fields, and labels in bold
Use angle brackets between UI labels for menu paths, such as File > Save As
Use italics for new terms on first use, sparingly and only when introducing the term
Use italics for publication titles
Format keyboard shortcuts in plain text, such as Press Ctrl+Alt+Delete
Use owner/repo link text for GitHub repositories, preferring [NVIDIA/NeMo](link) over prose references like 'the GitHub repo'
Introduce every code block with a complete sentence
Do not make a code block complete the grammar of the previous sentence
Do not continue a sentence after a code block
Use syntax highlighting when the format supports it for code blocks
Avoid the word 'snippet' unless the surrounding docs already use it as a term of art
Keep inline method, function, and class references consistent with nearby docs, omitting empty parentheses for prose readability when no call is shown
Use descriptive anchor text that matches the destination title when possible for links
Avoid raw URLs in running text
Avoid generic anchor text such as 'here,' 'this page,' and 'read more'
Include acronyms in link text when a linked term includes an acronym
Do not link long sentences or multiple sentences
Avoid links that pull readers away from a procedure unless the link is a p...

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (AGENTS.md)

SKILL.md files are skill entrypoints and must start with YAML frontmatter containing at least name and description.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

⚙️ CodeRabbit configuration file

**/SKILL.md: Do not flag SKILL.md files for missing SPDX headers. Skill entrypoints intentionally start with YAML frontmatter instead.
Verify that every SKILL.md keeps valid YAML frontmatter with at least name and description fields before the Markdown body.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (AGENTS.md)

Update README.md, fern/, package READMEs, and binding-support notes when public behavior, package names, examples, or supported bindings change.

**/*.{md,mdx}: Prefer the documented public API, not internal shortcuts
Keep package names, repo references, and build commands current
Keep release-process and release-notes guidance in repo-maintainer docs such as RELEASING.md, not as user-facing docs pages or CHANGELOG.md
Keep stable user-facing wrappers at scripts/ root in docs and examples; only point at namespaced helper paths when documenting internal maintenance work
When detailed dynamic plugin guides exist, keep Rust native plugin examples, Python worker plugin examples, and grpc-v1 protocol details on separate pages

If links in documentation change, run just docs-linkcheck.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• docs/nemo-relay-cli/codex.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Add the SPDX license header to all Markdown/MDX documentation files using the HTML comment block form.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• docs/nemo-relay-cli/codex.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

**/*: Format changed files with the language-native formatter before the final lint/test pass.
If dynamic plugin behavior changed, use maintain-dynamic-plugins and include the native SDK, worker protocol, Python SDK, docs, packaging, and Codecov surfaces in the validation plan.
If code changes alter APIs, bindings, commands, paths, packaging behavior, observability/adaptive semantics, or documented best practices, update any dependent maintainer or consumer skills in the same branch.
During iteration, prefer uv run pre-commit run --files <changed files...>.
Before review or handoff, run uv run pre-commit run --all-files.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• crates/core/tests/unit/context_tests.rs
• docs/nemo-relay-cli/codex.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• crates/cli/tests/coverage/adapters_tests.rs
• docs/nemo-relay-cli/basic-usage.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• docs/configure-plugins/observability/atof.mdx
• crates/core/src/api/runtime/state.rs
• docs/nemo-relay-cli/claude-code.mdx
• crates/cli/src/adapters/mod.rs
• docs/about-nemo-relay/concepts/events.mdx
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

⚙️ CodeRabbit configuration file

**:

AGENTS.md

This file provides guidance to agents, including Claude Code and OpenAI Codex, when working in this repository.

Project Overview

NeMo Relay is a multi-language agent runtime framework for execution scopes, lifecycle events, middleware, plugins, and observability around tool and LLM calls. The core runtime is Rust. Primary supported bindings are Rust, Python, and Node.js. Go and the raw C FFI are experimental and source-first.

The shared runtime model is:

1. Scope stacks decide where work belongs and which scope-local behavior is visible.
2. Middleware registries decide what guardrails and intercepts run around managed calls.
3. Plugins install reusable runtime behavior from configuration.
4. Events record runtime behavior in ATOF form.
5. Subscribers and exporters consume events in-process or export them to ATIF, OpenTelemetry, OpenInference, or other backends.

Repository Structure

The repository layout separates the Rust runtime, language bindings,
documentation, integrations, and agent-facing skills.

crates/
  core/       # Rust core runtime crate, published as nemo-relay
  adaptive/   # Adaptive runtime primitives and plugin components
  python/     # PyO3 native extension for the Python package
  ffi/        # Raw C ABI layer used by downstream bindings such as Go
  node/       # NAPI Node.js binding and JavaScript/TypeScript entry points
python/
  nemo_relay/  # Python wrapper package: scopes, tools, LLM, middleware, typed helpers, plugins, adaptive helpers
  tests/      # Python tests
go/
  nemo_relay/  # Experimental Go CGo binding and tests
fern/         # Fern documentation site
scripts/      # Stable wrappers and helper scripts; build/test/docs entry points live in justfile
skills/       # Published Codex/agent skills for NeMo Relay usage patterns

Prerequisites

Insta...

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• crates/core/tests/unit/context_tests.rs
• docs/nemo-relay-cli/codex.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• crates/cli/tests/coverage/adapters_tests.rs
• docs/nemo-relay-cli/basic-usage.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• docs/configure-plugins/observability/atof.mdx
• crates/core/src/api/runtime/state.rs
• docs/nemo-relay-cli/claude-code.mdx
• crates/cli/src/adapters/mod.rs
• docs/about-nemo-relay/concepts/events.mdx
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

**/*.rs: Any Rust change must run just test-rust
Any Rust change must run cargo fmt --all
Any Rust change must run cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all for all FFI work since it is Rust work
Run just test-rust to validate FFI changes
Run cargo clippy --workspace --all-targets -- -D warnings to enforce strict linting on FFI work

When Rust files changed as part of Go work, also run cargo fmt --all, just test-rust, and cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all when Rust files are changed as part of Node work
Run cargo clippy --workspace --all-targets -- -D warnings when Rust files are changed as part of Node work
Run just test-rust when Rust files are changed as part of Node work

When changing the core Rust runtime or Rust-facing API surface, format Rust code with cargo fmt (rustfmt defaults), keep cargo clippy -- -D warnings clean, and satisfy cargo deny check per deny.toml.

**/*.rs: If any Rust code changed, always run just test-rust.
If any Rust code changed, also run cargo fmt --all.
If any Rust code changed, also run cargo clippy --workspace --all-targets -- -D warnings.
For Rust changes headed for review, run cargo fmt --all and cargo clippy --workspace --all-targets -- -D warnings even if relying on pre-commit.

Files:

• crates/core/tests/unit/context_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/api/runtime/state.rs
• crates/cli/src/adapters/mod.rs
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

Changes to crates/core or crates/adaptive must run the full language matrix

Files:

• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/runtime/state.rs
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/test-go-binding/SKILL.md)

If the change touched crates/core or shared runtime semantics, also use validate-change for broader validation

Files:

• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/runtime/state.rs
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (AGENTS.md)

Follow binding naming conventions in Rust and Python: use snake_case.

Files:

• crates/core/tests/unit/context_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/api/runtime/state.rs
• crates/cli/src/adapters/mod.rs
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (AGENTS.md)

**/*.{rs,py,js,mjs,cjs,ts,tsx}: Use Json = serde_json::Value in Rust-facing runtime APIs where the existing code expects JSON payloads.
Use Result<T> with FlowError in core runtime paths, and keep errors explicit and binding-appropriate at the wrapper layer.
Keep async behavior on the existing tokio-based model; bindings should preserve callback and future lifetimes rather than blocking or hiding async work unexpectedly.

Files:

• crates/core/tests/unit/context_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/api/runtime/state.rs
• crates/cli/src/adapters/mod.rs
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Use language-appropriate naming conventions: Rust snake_case, C FFI exports prefixed nemo_relay_, Go PascalCase, Node.js camelCase, and Python snake_case.

Files:

• crates/core/tests/unit/context_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/api/runtime/state.rs
• crates/cli/src/adapters/mod.rs
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Add the SPDX license header to all Rust, Go, JavaScript, and TypeScript source files using the corresponding // comment form.

Files:

• crates/core/tests/unit/context_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/api/runtime/state.rs
• crates/cli/src/adapters/mod.rs
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If crates/core or crates/adaptive changed, run the full validation matrix across Rust, Python, Go, and Node.js.

Files:

• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/runtime/state.rs
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If a language surface changed, always run that language's test target even when Rust core did not change.

Files:

• crates/core/tests/unit/context_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/api/runtime/state.rs
• crates/cli/src/adapters/mod.rs
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

⚙️ CodeRabbit configuration file

crates/{core,adaptive}/**/*.rs: Review the Rust runtime for async correctness, scope isolation, middleware ordering, and event lifecycle regressions.
Pay close attention to task-local/thread-local scope propagation, callback lifetimes, stream finalization, and root_uuid isolation.
Public API changes should preserve existing behavior unless tests and docs show the intended migration path.

Files:

• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/runtime/state.rs
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

⚙️ CodeRabbit configuration file

{crates/**/tests/**,python/tests/**,go/nemo_relay/**/*_test.go}: Tests should cover the behavior promised by the changed API surface, including error paths and cross-request isolation where relevant.
Prefer assertions on lifecycle events, scope stacks, middleware ordering, and binding parity over shallow smoke tests.

Files:

• crates/core/tests/unit/context_tests.rs
• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/tests/unit/observability/atof_tests.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/SKILL.md)

MDX top-of-file SPDX comments must use {/* ... */} delimiters instead of HTML comment delimiters (Must-Fix)

In MDX files, top-of-file comments must use JSX comment delimiters ({/* to open and */} to close); do not use HTML comments for MDX SPDX headers

Files:

• docs/nemo-relay-cli/codex.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update docs and examples.

Files:

• docs/nemo-relay-cli/codex.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If documentation examples or commands under docs/ change, run the targeted docs checks appropriate to the change.

Files:

• docs/nemo-relay-cli/codex.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/about-nemo-relay/concepts/events.mdx

⚙️ CodeRabbit configuration file

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}: Review documentation for technical accuracy against the current API, command correctness, and consistency across language bindings.
Flag stale examples, missing SPDX headers where required, and instructions that no longer match CI or pre-commit behavior.

Files:

• docs/nemo-relay-cli/codex.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (.agents/skills/add-middleware/SKILL.md)

crates/core/src/api/runtime/state.rs: Add registry fields as SortedRegistry<GuardrailEntry<T>> or SortedRegistry<Intercept<T>> to NemoRelayContextState in crates/core/src/api/runtime/state.rs
Add chain execution helpers to NemoRelayContextState following the pattern of existing methods like tool_sanitize_request_chain or tool_request_intercepts_chain

Files:

• crates/core/src/api/runtime/state.rs

📄 CodeRabbit inference engine (.agents/skills/add-binding-feature/SKILL.md)

Implement the new or changed public runtime behavior first in the Rust core, especially under crates/core/src/api/ and related core modules such as crates/core/src/api/runtime/, crates/core/src/codec/, and crates/core/src/json.rs.

Files:

• crates/core/src/api/runtime/state.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (.agents/skills/maintain-dynamic-plugins/SKILL.md)

Do not add tests under src; Rust tests belong in crate tests/ trees, and Python SDK tests belong under python/tests.

Files:

• crates/core/src/api/runtime/state.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (.agents/skills/add-middleware/SKILL.md)

Wire the new middleware chain into the execute path in crates/core/src/api/tool.rs or crates/core/src/api/llm.rs at the appropriate pipeline stage

Files:

• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

**/*.rs: Any Rust change must run just test-rust
Any Rust change must run cargo fmt --all
Any Rust change must run cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all for all FFI work since it is Rust work
Run just test-rust to validate FFI changes
Run cargo clippy --workspace --all-targets -- -D warnings to enforce strict linting on FFI work

When Rust files changed as part of Go work, also run cargo fmt --all, just test-rust, and cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all when Rust files are changed as part of Node work
Run cargo clippy --workspace --all-targets -- -D warnings when Rust files are changed as part of Node work
Run just test-rust when Rust files are changed as part of Node work

When changing the core Rust runtime or Rust-facing API surface, format Rust code with cargo fmt (rustfmt defaults), keep cargo clippy -- -D warnings clean, and satisfy cargo deny check per deny.toml.

**/*.rs: If any Rust code changed, always run just test-rust.
If any Rust code changed, also run cargo fmt --all.
If any Rust code changed, also run cargo clippy --workspace --all-targets -- -D warnings.
For Rust changes headed for review, run cargo fmt --all and cargo clippy --workspace --all-targets -- -D warnings even if relying on pre-commit.

Files:

• crates/core/src/codec/openai_chat.rs
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

Changes to crates/core or crates/adaptive must run the full language matrix

Files:

• crates/core/src/codec/openai_chat.rs
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/test-go-binding/SKILL.md)

If the change touched crates/core or shared runtime semantics, also use validate-change for broader validation

Files:

• crates/core/src/codec/openai_chat.rs
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (AGENTS.md)

Follow binding naming conventions in Rust and Python: use snake_case.

Files:

• crates/core/src/codec/openai_chat.rs
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (AGENTS.md)

**/*.{rs,py,js,mjs,cjs,ts,tsx}: Use Json = serde_json::Value in Rust-facing runtime APIs where the existing code expects JSON payloads.
Use Result<T> with FlowError in core runtime paths, and keep errors explicit and binding-appropriate at the wrapper layer.
Keep async behavior on the existing tokio-based model; bindings should preserve callback and future lifetimes rather than blocking or hiding async work unexpectedly.

Files:

• crates/core/src/codec/openai_chat.rs
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Use language-appropriate naming conventions: Rust snake_case, C FFI exports prefixed nemo_relay_, Go PascalCase, Node.js camelCase, and Python snake_case.

Files:

• crates/core/src/codec/openai_chat.rs
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Add the SPDX license header to all Rust, Go, JavaScript, and TypeScript source files using the corresponding // comment form.

Files:

• crates/core/src/codec/openai_chat.rs
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/add-binding-feature/SKILL.md)

Implement the new or changed public runtime behavior first in the Rust core, especially under crates/core/src/api/ and related core modules such as crates/core/src/api/runtime/, crates/core/src/codec/, and crates/core/src/json.rs.

Files:

• crates/core/src/codec/openai_chat.rs
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/maintain-dynamic-plugins/SKILL.md)

Do not add tests under src; Rust tests belong in crate tests/ trees, and Python SDK tests belong under python/tests.

Files:

• crates/core/src/codec/openai_chat.rs
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

**/*: Format changed files with the language-native formatter before the final lint/test pass.
If dynamic plugin behavior changed, use maintain-dynamic-plugins and include the native SDK, worker protocol, Python SDK, docs, packaging, and Codecov surfaces in the validation plan.
If code changes alter APIs, bindings, commands, paths, packaging behavior, observability/adaptive semantics, or documented best practices, update any dependent maintainer or consumer skills in the same branch.
During iteration, prefer uv run pre-commit run --files <changed files...>.
Before review or handoff, run uv run pre-commit run --all-files.

Files:

• crates/core/src/codec/openai_chat.rs
• docs/instrument-applications/instrument-llm-call.mdx
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• docs/about-nemo-relay/concepts/events.mdx
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If crates/core or crates/adaptive changed, run the full validation matrix across Rust, Python, Go, and Node.js.

Files:

• crates/core/src/codec/openai_chat.rs
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If a language surface changed, always run that language's test target even when Rust core did not change.

Files:

• crates/core/src/codec/openai_chat.rs
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

⚙️ CodeRabbit configuration file

**:

AGENTS.md

This file provides guidance to agents, including Claude Code and OpenAI Codex, when working in this repository.

Project Overview

NeMo Relay is a multi-language agent runtime framework for execution scopes, lifecycle events, middleware, plugins, and observability around tool and LLM calls. The core runtime is Rust. Primary supported bindings are Rust, Python, and Node.js. Go and the raw C FFI are experimental and source-first.

The shared runtime model is:

1. Scope stacks decide where work belongs and which scope-local behavior is visible.
2. Middleware registries decide what guardrails and intercepts run around managed calls.
3. Plugins install reusable runtime behavior from configuration.
4. Events record runtime behavior in ATOF form.
5. Subscribers and exporters consume events in-process or export them to ATIF, OpenTelemetry, OpenInference, or other backends.

Repository Structure

The repository layout separates the Rust runtime, language bindings,
documentation, integrations, and agent-facing skills.

crates/
  core/       # Rust core runtime crate, published as nemo-relay
  adaptive/   # Adaptive runtime primitives and plugin components
  python/     # PyO3 native extension for the Python package
  ffi/        # Raw C ABI layer used by downstream bindings such as Go
  node/       # NAPI Node.js binding and JavaScript/TypeScript entry points
python/
  nemo_relay/  # Python wrapper package: scopes, tools, LLM, middleware, typed helpers, plugins, adaptive helpers
  tests/      # Python tests
go/
  nemo_relay/  # Experimental Go CGo binding and tests
fern/         # Fern documentation site
scripts/      # Stable wrappers and helper scripts; build/test/docs entry points live in justfile
skills/       # Published Codex/agent skills for NeMo Relay usage patterns

Prerequisites

Insta...

Files:

• crates/core/src/codec/openai_chat.rs
• docs/instrument-applications/instrument-llm-call.mdx
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• docs/about-nemo-relay/concepts/events.mdx
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

⚙️ CodeRabbit configuration file

crates/{core,adaptive}/**/*.rs: Review the Rust runtime for async correctness, scope isolation, middleware ordering, and event lifecycle regressions.
Pay close attention to task-local/thread-local scope propagation, callback lifetimes, stream finalization, and root_uuid isolation.
Public API changes should preserve existing behavior unless tests and docs show the intended migration path.

Files:

• crates/core/src/codec/openai_chat.rs
• crates/core/src/codec/openai_responses.rs
• crates/core/src/codec/anthropic.rs
• crates/core/src/codec/resolve.rs
• crates/core/src/api/runtime/state.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/SKILL.md)

MDX top-of-file SPDX comments must use {/* ... */} delimiters instead of HTML comment delimiters (Must-Fix)

In MDX files, top-of-file comments must use JSX comment delimiters ({/* to open and */} to close); do not use HTML comments for MDX SPDX headers

Files:

• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (AGENTS.md)

Update README.md, fern/, package READMEs, and binding-support notes when public behavior, package names, examples, or supported bindings change.

**/*.{md,mdx}: Prefer the documented public API, not internal shortcuts
Keep package names, repo references, and build commands current
Keep release-process and release-notes guidance in repo-maintainer docs such as RELEASING.md, not as user-facing docs pages or CHANGELOG.md
Keep stable user-facing wrappers at scripts/ root in docs and examples; only point at namespaced helper paths when documenting internal maintenance work
When detailed dynamic plugin guides exist, keep Rust native plugin examples, Python worker plugin examples, and grpc-v1 protocol details on separate pages

If links in documentation change, run just docs-linkcheck.

Files:

• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Add the SPDX license header to all Markdown/MDX documentation files using the HTML comment block form.

Files:

• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update docs and examples.

Files:

• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If documentation examples or commands under docs/ change, run the targeted docs checks appropriate to the change.

Files:

• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx

⚙️ CodeRabbit configuration file

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}: Review documentation for technical accuracy against the current API, command correctness, and consistency across language bindings.
Flag stale examples, missing SPDX headers where required, and instructions that no longer match CI or pre-commit behavior.

Files:

• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (.agents/skills/add-middleware/SKILL.md)

crates/core/src/api/runtime/state.rs: Add registry fields as SortedRegistry<GuardrailEntry<T>> or SortedRegistry<Intercept<T>> to NemoRelayContextState in crates/core/src/api/runtime/state.rs
Add chain execution helpers to NemoRelayContextState following the pattern of existing methods like tool_sanitize_request_chain or tool_request_intercepts_chain

Files:

• crates/core/src/api/runtime/state.rs

⚙️ CodeRabbit configuration file

{crates/**/tests/**,python/tests/**,go/nemo_relay/**/*_test.go}: Tests should cover the behavior promised by the changed API surface, including error paths and cross-request isolation where relevant.
Prefer assertions on lifecycle events, scope stacks, middleware ordering, and binding parity over shallow smoke tests.

Files:

• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/add-middleware/SKILL.md)

Wire the new middleware chain into the execute path in crates/core/src/api/tool.rs or crates/core/src/api/llm.rs at the appropriate pipeline stage

Files:

• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

**/*.rs: Any Rust change must run just test-rust
Any Rust change must run cargo fmt --all
Any Rust change must run cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all for all FFI work since it is Rust work
Run just test-rust to validate FFI changes
Run cargo clippy --workspace --all-targets -- -D warnings to enforce strict linting on FFI work

When Rust files changed as part of Go work, also run cargo fmt --all, just test-rust, and cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all when Rust files are changed as part of Node work
Run cargo clippy --workspace --all-targets -- -D warnings when Rust files are changed as part of Node work
Run just test-rust when Rust files are changed as part of Node work

When changing the core Rust runtime or Rust-facing API surface, format Rust code with cargo fmt (rustfmt defaults), keep cargo clippy -- -D warnings clean, and satisfy cargo deny check per deny.toml.

**/*.rs: If any Rust code changed, always run just test-rust.
If any Rust code changed, also run cargo fmt --all.
If any Rust code changed, also run cargo clippy --workspace --all-targets -- -D warnings.
For Rust changes headed for review, run cargo fmt --all and cargo clippy --workspace --all-targets -- -D warnings even if relying on pre-commit.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/tests/unit/context_tests.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (AGENTS.md)

Follow binding naming conventions in Rust and Python: use snake_case.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/tests/unit/context_tests.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (AGENTS.md)

**/*.{rs,py,js,mjs,cjs,ts,tsx}: Use Json = serde_json::Value in Rust-facing runtime APIs where the existing code expects JSON payloads.
Use Result<T> with FlowError in core runtime paths, and keep errors explicit and binding-appropriate at the wrapper layer.
Keep async behavior on the existing tokio-based model; bindings should preserve callback and future lifetimes rather than blocking or hiding async work unexpectedly.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/tests/unit/context_tests.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Use language-appropriate naming conventions: Rust snake_case, C FFI exports prefixed nemo_relay_, Go PascalCase, Node.js camelCase, and Python snake_case.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/tests/unit/context_tests.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Add the SPDX license header to all Rust, Go, JavaScript, and TypeScript source files using the corresponding // comment form.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/tests/unit/context_tests.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

**/*: Format changed files with the language-native formatter before the final lint/test pass.
If dynamic plugin behavior changed, use maintain-dynamic-plugins and include the native SDK, worker protocol, Python SDK, docs, packaging, and Codecov surfaces in the validation plan.
If code changes alter APIs, bindings, commands, paths, packaging behavior, observability/adaptive semantics, or documented best practices, update any dependent maintainer or consumer skills in the same branch.
During iteration, prefer uv run pre-commit run --files <changed files...>.
Before review or handoff, run uv run pre-commit run --all-files.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• skills/nemo-relay-setup-observability/SKILL.md
• crates/core/tests/unit/context_tests.rs
• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• docs/nemo-relay-cli/claude-code.mdx
• docs/nemo-relay-cli/codex.mdx
• docs/about-nemo-relay/concepts/events.mdx
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/scope.rs
• docs/configure-plugins/observability/atof.mdx
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If a language surface changed, always run that language's test target even when Rust core did not change.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/tests/unit/context_tests.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/runtime/scope_stack.rs

⚙️ CodeRabbit configuration file

**:

AGENTS.md

This file provides guidance to agents, including Claude Code and OpenAI Codex, when working in this repository.

Project Overview

NeMo Relay is a multi-language agent runtime framework for execution scopes, lifecycle events, middleware, plugins, and observability around tool and LLM calls. The core runtime is Rust. Primary supported bindings are Rust, Python, and Node.js. Go and the raw C FFI are experimental and source-first.

The shared runtime model is:

1. Scope stacks decide where work belongs and which scope-local behavior is visible.
2. Middleware registries decide what guardrails and intercepts run around managed calls.
3. Plugins install reusable runtime behavior from configuration.
4. Events record runtime behavior in ATOF form.
5. Subscribers and exporters consume events in-process or export them to ATIF, OpenTelemetry, OpenInference, or other backends.

Repository Structure

The repository layout separates the Rust runtime, language bindings,
documentation, integrations, and agent-facing skills.

crates/
  core/       # Rust core runtime crate, published as nemo-relay
  adaptive/   # Adaptive runtime primitives and plugin components
  python/     # PyO3 native extension for the Python package
  ffi/        # Raw C ABI layer used by downstream bindings such as Go
  node/       # NAPI Node.js binding and JavaScript/TypeScript entry points
python/
  nemo_relay/  # Python wrapper package: scopes, tools, LLM, middleware, typed helpers, plugins, adaptive helpers
  tests/      # Python tests
go/
  nemo_relay/  # Experimental Go CGo binding and tests
fern/         # Fern documentation site
scripts/      # Stable wrappers and helper scripts; build/test/docs entry points live in justfile
skills/       # Published Codex/agent skills for NeMo Relay usage patterns

Prerequisites

Insta...

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• skills/nemo-relay-setup-observability/SKILL.md
• crates/core/tests/unit/context_tests.rs
• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• docs/nemo-relay-cli/claude-code.mdx
• docs/nemo-relay-cli/codex.mdx
• docs/about-nemo-relay/concepts/events.mdx
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/scope.rs
• docs/configure-plugins/observability/atof.mdx
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/runtime/scope_stack.rs

⚙️ CodeRabbit configuration file

{crates/**/tests/**,python/tests/**,go/nemo_relay/**/*_test.go}: Tests should cover the behavior promised by the changed API surface, including error paths and cross-request isolation where relevant.
Prefer assertions on lifecycle events, scope stacks, middleware ordering, and binding parity over shallow smoke tests.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

**/*.{md,rst,html,txt}: Always spell NVIDIA in all caps. Do not use Nvidia, nvidia, nVidia, nVIDIA, or NV.
Use an NVIDIA before a noun because the name starts with an 'en' sound.
Do not add a registered trademark symbol after NVIDIA when referring to the company.
Use trademark symbols with product names only when the document type or legal guidance requires them.
Verify official capitalization, spacing, and hyphenation for product names.
Precede NVIDIA product names with NVIDIA on first mention when it is natural and accurate.
Do not rewrite product names for grammar or title-case rules.
Preserve third-party product names according to the owner's spelling.
Include the company name and full model qualifier on first use when it helps identify the model.
Preserve the official capitalization and punctuation of model names.
Use shorter family names only after the full name is established.
Spell out a term on first use and put the acronym in parentheses unless the acronym is widely understood by the intended audience.
Use the acronym on later mentions after it has been defined.
For long documents, reintroduce the full term if readers might lose context.
Form plurals of acronyms with s, not an apostrophe, such as GPUs.
In headings, common acronyms can remain abbreviated. Spell out the term in the first or second sentence of the body.
Common terms such as CPU, GPU, PC, API, and UI usually do not need to be spelled out for developer audiences.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

Link the first mention of a product name when the destination helps the reader.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

Spell NVIDIA in all caps. Do not use Nvidia, nvidia, or NV.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

**/*.{md,rst}: Format commands, code elements, expressions, package names, file names, and paths as inline code.
Use descriptive link text. Avoid raw URLs and weak anchors such as "here" or "read more."
Use title case consistently for technical documentation headings.
Introduce code blocks, lists, tables, and images with complete sentences.
Write procedures as imperative steps. Keep steps parallel and split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English.
Use can for possibility and reserve may for permission.
Use after for temporal relationships instead of once.
Prefer refer to over see when the wording points readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical docs.
Spell out months in body text, avoid ordinal dates, and use clear time zones.
Spell out whole numbers from zero through nine unless they are technical values, parameters, versions, or UI values.
Use numerals for 10 or greater and include commas in thousands.
Do not add trademark symbols to learning-oriented docs unless the source, platform, or legal guidance explicitly requires them.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-technical-docs.md)

**/*.md: Use title case consistently in technical documentation headings
Avoid quotation marks, ampersands, and exclamation marks in headings
Keep product, event, research, and whitepaper names in their official title case
Use title case for table headers
Do not force social-media sentence case into technical docs
Format code elements, commands, parameters, package names, and expressions in monospace
Format directories, file names, and paths in monospace using backticks
Use angle brackets inside monospace for variables inside paths, such as /home/<username>/.login
Format error messages and strings in quotation marks, keeping literal code strings in code formatting when clearer
Format UI buttons, menus, fields, and labels in bold
Use angle brackets between UI labels for menu paths, such as File > Save As
Use italics for new terms on first use, sparingly and only when introducing the term
Use italics for publication titles
Format keyboard shortcuts in plain text, such as Press Ctrl+Alt+Delete
Use owner/repo link text for GitHub repositories, preferring [NVIDIA/NeMo](link) over prose references like 'the GitHub repo'
Introduce every code block with a complete sentence
Do not make a code block complete the grammar of the previous sentence
Do not continue a sentence after a code block
Use syntax highlighting when the format supports it for code blocks
Avoid the word 'snippet' unless the surrounding docs already use it as a term of art
Keep inline method, function, and class references consistent with nearby docs, omitting empty parentheses for prose readability when no call is shown
Use descriptive anchor text that matches the destination title when possible for links
Avoid raw URLs in running text
Avoid generic anchor text such as 'here,' 'this page,' and 'read more'
Include acronyms in link text when a linked term includes an acronym
Do not link long sentences or multiple sentences
Avoid links that pull readers away from a procedure unless the link is a p...

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

📄 CodeRabbit inference engine (AGENTS.md)

SKILL.md files are skill entrypoints and must start with YAML frontmatter containing at least name and description.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

⚙️ CodeRabbit configuration file

**/SKILL.md: Do not flag SKILL.md files for missing SPDX headers. Skill entrypoints intentionally start with YAML frontmatter instead.
Verify that every SKILL.md keeps valid YAML frontmatter with at least name and description fields before the Markdown body.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

📄 CodeRabbit inference engine (AGENTS.md)

Update README.md, fern/, package READMEs, and binding-support notes when public behavior, package names, examples, or supported bindings change.

**/*.{md,mdx}: Prefer the documented public API, not internal shortcuts
Keep package names, repo references, and build commands current
Keep release-process and release-notes guidance in repo-maintainer docs such as RELEASING.md, not as user-facing docs pages or CHANGELOG.md
Keep stable user-facing wrappers at scripts/ root in docs and examples; only point at namespaced helper paths when documenting internal maintenance work
When detailed dynamic plugin guides exist, keep Rust native plugin examples, Python worker plugin examples, and grpc-v1 protocol details on separate pages

If links in documentation change, run just docs-linkcheck.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• docs/nemo-relay-cli/claude-code.mdx
• docs/nemo-relay-cli/codex.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Add the SPDX license header to all Markdown/MDX documentation files using the HTML comment block form.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• docs/nemo-relay-cli/claude-code.mdx
• docs/nemo-relay-cli/codex.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

Changes to crates/core or crates/adaptive must run the full language matrix

Files:

• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (.agents/skills/test-go-binding/SKILL.md)

If the change touched crates/core or shared runtime semantics, also use validate-change for broader validation

Files:

• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If crates/core or crates/adaptive changed, run the full validation matrix across Rust, Python, Go, and Node.js.

Files:

• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/runtime/scope_stack.rs

⚙️ CodeRabbit configuration file

crates/{core,adaptive}/**/*.rs: Review the Rust runtime for async correctness, scope isolation, middleware ordering, and event lifecycle regressions.
Pay close attention to task-local/thread-local scope propagation, callback lifetimes, stream finalization, and root_uuid isolation.
Public API changes should preserve existing behavior unless tests and docs show the intended migration path.

Files:

• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/SKILL.md)

MDX top-of-file SPDX comments must use {/* ... */} delimiters instead of HTML comment delimiters (Must-Fix)

In MDX files, top-of-file comments must use JSX comment delimiters ({/* to open and */} to close); do not use HTML comments for MDX SPDX headers

Files:

• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/nemo-relay-cli/codex.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update docs and examples.

Files:

• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/nemo-relay-cli/codex.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If documentation examples or commands under docs/ change, run the targeted docs checks appropriate to the change.

Files:

• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/nemo-relay-cli/codex.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx

⚙️ CodeRabbit configuration file

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}: Review documentation for technical accuracy against the current API, command correctness, and consistency across language bindings.
Flag stale examples, missing SPDX headers where required, and instructions that no longer match CI or pre-commit behavior.

Files:

• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/nemo-relay-cli/codex.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/configure-plugins/observability/atof.mdx

📄 CodeRabbit inference engine (.agents/skills/maintain-dynamic-plugins/SKILL.md)

Do not add tests under src; Rust tests belong in crate tests/ trees, and Python SDK tests belong under python/tests.

Files:

• crates/cli/src/adapters/mod.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (.agents/skills/add-binding-feature/SKILL.md)

Implement the new or changed public runtime behavior first in the Rust core, especially under crates/core/src/api/ and related core modules such as crates/core/src/api/runtime/, crates/core/src/codec/, and crates/core/src/json.rs.

Files:

• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (.agents/skills/add-middleware/SKILL.md)

Wire the new middleware chain into the execute path in crates/core/src/api/tool.rs or crates/core/src/api/llm.rs at the appropriate pipeline stage

Files:

• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/SKILL.md)

MDX top-of-file SPDX comments must use {/* ... */} delimiters instead of HTML comment delimiters (Must-Fix)

In MDX files, top-of-file comments must use JSX comment delimiters ({/* to open and */} to close); do not use HTML comments for MDX SPDX headers

Files:

• docs/nemo-relay-cli/basic-usage.mdx
• docs/nemo-relay-cli/codex.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx

📄 CodeRabbit inference engine (AGENTS.md)

Update README.md, fern/, package READMEs, and binding-support notes when public behavior, package names, examples, or supported bindings change.

**/*.{md,mdx}: Prefer the documented public API, not internal shortcuts
Keep package names, repo references, and build commands current
Keep release-process and release-notes guidance in repo-maintainer docs such as RELEASING.md, not as user-facing docs pages or CHANGELOG.md
Keep stable user-facing wrappers at scripts/ root in docs and examples; only point at namespaced helper paths when documenting internal maintenance work
When detailed dynamic plugin guides exist, keep Rust native plugin examples, Python worker plugin examples, and grpc-v1 protocol details on separate pages

If links in documentation change, run just docs-linkcheck.

Files:

• docs/nemo-relay-cli/basic-usage.mdx
• docs/nemo-relay-cli/codex.mdx
• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• docs/about-nemo-relay/concepts/events.mdx
• skills/nemo-relay-export-openinference/SKILL.md
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Add the SPDX license header to all Markdown/MDX documentation files using the HTML comment block form.

Files:

• docs/nemo-relay-cli/basic-usage.mdx
• docs/nemo-relay-cli/codex.mdx
• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• docs/about-nemo-relay/concepts/events.mdx
• skills/nemo-relay-export-openinference/SKILL.md
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update docs and examples.

Files:

• docs/nemo-relay-cli/basic-usage.mdx
• docs/nemo-relay-cli/codex.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

**/*: Format changed files with the language-native formatter before the final lint/test pass.
If dynamic plugin behavior changed, use maintain-dynamic-plugins and include the native SDK, worker protocol, Python SDK, docs, packaging, and Codecov surfaces in the validation plan.
If code changes alter APIs, bindings, commands, paths, packaging behavior, observability/adaptive semantics, or documented best practices, update any dependent maintainer or consumer skills in the same branch.
During iteration, prefer uv run pre-commit run --files <changed files...>.
Before review or handoff, run uv run pre-commit run --all-files.

Files:

• docs/nemo-relay-cli/basic-usage.mdx
• docs/nemo-relay-cli/codex.mdx
• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/src/adapters/mod.rs
• docs/about-nemo-relay/concepts/events.mdx
• skills/nemo-relay-export-openinference/SKILL.md
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/claude-code.mdx
• crates/core/tests/unit/context_tests.rs
• docs/configure-plugins/observability/atof.mdx
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If documentation examples or commands under docs/ change, run the targeted docs checks appropriate to the change.

Files:

• docs/nemo-relay-cli/basic-usage.mdx
• docs/nemo-relay-cli/codex.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx

⚙️ CodeRabbit configuration file

**:

AGENTS.md

This file provides guidance to agents, including Claude Code and OpenAI Codex, when working in this repository.

Project Overview

NeMo Relay is a multi-language agent runtime framework for execution scopes, lifecycle events, middleware, plugins, and observability around tool and LLM calls. The core runtime is Rust. Primary supported bindings are Rust, Python, and Node.js. Go and the raw C FFI are experimental and source-first.

The shared runtime model is:

1. Scope stacks decide where work belongs and which scope-local behavior is visible.
2. Middleware registries decide what guardrails and intercepts run around managed calls.
3. Plugins install reusable runtime behavior from configuration.
4. Events record runtime behavior in ATOF form.
5. Subscribers and exporters consume events in-process or export them to ATIF, OpenTelemetry, OpenInference, or other backends.

Repository Structure

The repository layout separates the Rust runtime, language bindings,
documentation, integrations, and agent-facing skills.

crates/
  core/       # Rust core runtime crate, published as nemo-relay
  adaptive/   # Adaptive runtime primitives and plugin components
  python/     # PyO3 native extension for the Python package
  ffi/        # Raw C ABI layer used by downstream bindings such as Go
  node/       # NAPI Node.js binding and JavaScript/TypeScript entry points
python/
  nemo_relay/  # Python wrapper package: scopes, tools, LLM, middleware, typed helpers, plugins, adaptive helpers
  tests/      # Python tests
go/
  nemo_relay/  # Experimental Go CGo binding and tests
fern/         # Fern documentation site
scripts/      # Stable wrappers and helper scripts; build/test/docs entry points live in justfile
skills/       # Published Codex/agent skills for NeMo Relay usage patterns

Prerequisites

Insta...

Files:

• docs/nemo-relay-cli/basic-usage.mdx
• docs/nemo-relay-cli/codex.mdx
• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/src/adapters/mod.rs
• docs/about-nemo-relay/concepts/events.mdx
• skills/nemo-relay-export-openinference/SKILL.md
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/claude-code.mdx
• crates/core/tests/unit/context_tests.rs
• docs/configure-plugins/observability/atof.mdx
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

⚙️ CodeRabbit configuration file

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}: Review documentation for technical accuracy against the current API, command correctness, and consistency across language bindings.
Flag stale examples, missing SPDX headers where required, and instructions that no longer match CI or pre-commit behavior.

Files:

• docs/nemo-relay-cli/basic-usage.mdx
• docs/nemo-relay-cli/codex.mdx
• docs/about-nemo-relay/concepts/events.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

**/*.{md,rst,html,txt}: Always spell NVIDIA in all caps. Do not use Nvidia, nvidia, nVidia, nVIDIA, or NV.
Use an NVIDIA before a noun because the name starts with an 'en' sound.
Do not add a registered trademark symbol after NVIDIA when referring to the company.
Use trademark symbols with product names only when the document type or legal guidance requires them.
Verify official capitalization, spacing, and hyphenation for product names.
Precede NVIDIA product names with NVIDIA on first mention when it is natural and accurate.
Do not rewrite product names for grammar or title-case rules.
Preserve third-party product names according to the owner's spelling.
Include the company name and full model qualifier on first use when it helps identify the model.
Preserve the official capitalization and punctuation of model names.
Use shorter family names only after the full name is established.
Spell out a term on first use and put the acronym in parentheses unless the acronym is widely understood by the intended audience.
Use the acronym on later mentions after it has been defined.
For long documents, reintroduce the full term if readers might lose context.
Form plurals of acronyms with s, not an apostrophe, such as GPUs.
In headings, common acronyms can remain abbreviated. Spell out the term in the first or second sentence of the body.
Common terms such as CPU, GPU, PC, API, and UI usually do not need to be spelled out for developer audiences.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

Link the first mention of a product name when the destination helps the reader.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

Spell NVIDIA in all caps. Do not use Nvidia, nvidia, or NV.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

**/*.{md,rst}: Format commands, code elements, expressions, package names, file names, and paths as inline code.
Use descriptive link text. Avoid raw URLs and weak anchors such as "here" or "read more."
Use title case consistently for technical documentation headings.
Introduce code blocks, lists, tables, and images with complete sentences.
Write procedures as imperative steps. Keep steps parallel and split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English.
Use can for possibility and reserve may for permission.
Use after for temporal relationships instead of once.
Prefer refer to over see when the wording points readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical docs.
Spell out months in body text, avoid ordinal dates, and use clear time zones.
Spell out whole numbers from zero through nine unless they are technical values, parameters, versions, or UI values.
Use numerals for 10 or greater and include commas in thousands.
Do not add trademark symbols to learning-oriented docs unless the source, platform, or legal guidance explicitly requires them.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-technical-docs.md)

**/*.md: Use title case consistently in technical documentation headings
Avoid quotation marks, ampersands, and exclamation marks in headings
Keep product, event, research, and whitepaper names in their official title case
Use title case for table headers
Do not force social-media sentence case into technical docs
Format code elements, commands, parameters, package names, and expressions in monospace
Format directories, file names, and paths in monospace using backticks
Use angle brackets inside monospace for variables inside paths, such as /home/<username>/.login
Format error messages and strings in quotation marks, keeping literal code strings in code formatting when clearer
Format UI buttons, menus, fields, and labels in bold
Use angle brackets between UI labels for menu paths, such as File > Save As
Use italics for new terms on first use, sparingly and only when introducing the term
Use italics for publication titles
Format keyboard shortcuts in plain text, such as Press Ctrl+Alt+Delete
Use owner/repo link text for GitHub repositories, preferring [NVIDIA/NeMo](link) over prose references like 'the GitHub repo'
Introduce every code block with a complete sentence
Do not make a code block complete the grammar of the previous sentence
Do not continue a sentence after a code block
Use syntax highlighting when the format supports it for code blocks
Avoid the word 'snippet' unless the surrounding docs already use it as a term of art
Keep inline method, function, and class references consistent with nearby docs, omitting empty parentheses for prose readability when no call is shown
Use descriptive anchor text that matches the destination title when possible for links
Avoid raw URLs in running text
Avoid generic anchor text such as 'here,' 'this page,' and 'read more'
Include acronyms in link text when a linked term includes an acronym
Do not link long sentences or multiple sentences
Avoid links that pull readers away from a procedure unless the link is a p...

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

📄 CodeRabbit inference engine (AGENTS.md)

SKILL.md files are skill entrypoints and must start with YAML frontmatter containing at least name and description.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

⚙️ CodeRabbit configuration file

**/SKILL.md: Do not flag SKILL.md files for missing SPDX headers. Skill entrypoints intentionally start with YAML frontmatter instead.
Verify that every SKILL.md keeps valid YAML frontmatter with at least name and description fields before the Markdown body.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

**/*.rs: Any Rust change must run just test-rust
Any Rust change must run cargo fmt --all
Any Rust change must run cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all for all FFI work since it is Rust work
Run just test-rust to validate FFI changes
Run cargo clippy --workspace --all-targets -- -D warnings to enforce strict linting on FFI work

When Rust files changed as part of Go work, also run cargo fmt --all, just test-rust, and cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all when Rust files are changed as part of Node work
Run cargo clippy --workspace --all-targets -- -D warnings when Rust files are changed as part of Node work
Run just test-rust when Rust files are changed as part of Node work

When changing the core Rust runtime or Rust-facing API surface, format Rust code with cargo fmt (rustfmt defaults), keep cargo clippy -- -D warnings clean, and satisfy cargo deny check per deny.toml.

**/*.rs: If any Rust code changed, always run just test-rust.
If any Rust code changed, also run cargo fmt --all.
If any Rust code changed, also run cargo clippy --workspace --all-targets -- -D warnings.
For Rust changes headed for review, run cargo fmt --all and cargo clippy --workspace --all-targets -- -D warnings even if relying on pre-commit.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/src/adapters/mod.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (AGENTS.md)

Follow binding naming conventions in Rust and Python: use snake_case.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/src/adapters/mod.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (AGENTS.md)

**/*.{rs,py,js,mjs,cjs,ts,tsx}: Use Json = serde_json::Value in Rust-facing runtime APIs where the existing code expects JSON payloads.
Use Result<T> with FlowError in core runtime paths, and keep errors explicit and binding-appropriate at the wrapper layer.
Keep async behavior on the existing tokio-based model; bindings should preserve callback and future lifetimes rather than blocking or hiding async work unexpectedly.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/src/adapters/mod.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Use language-appropriate naming conventions: Rust snake_case, C FFI exports prefixed nemo_relay_, Go PascalCase, Node.js camelCase, and Python snake_case.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/src/adapters/mod.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Add the SPDX license header to all Rust, Go, JavaScript, and TypeScript source files using the corresponding // comment form.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/src/adapters/mod.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If a language surface changed, always run that language's test target even when Rust core did not change.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/cli/src/adapters/mod.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

⚙️ CodeRabbit configuration file

{crates/**/tests/**,python/tests/**,go/nemo_relay/**/*_test.go}: Tests should cover the behavior promised by the changed API surface, including error paths and cross-request isolation where relevant.
Prefer assertions on lifecycle events, scope stacks, middleware ordering, and binding parity over shallow smoke tests.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/maintain-dynamic-plugins/SKILL.md)

Do not add tests under src; Rust tests belong in crate tests/ trees, and Python SDK tests belong under python/tests.

Files:

• crates/cli/src/adapters/mod.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

Changes to crates/core or crates/adaptive must run the full language matrix

Files:

• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/test-go-binding/SKILL.md)

If the change touched crates/core or shared runtime semantics, also use validate-change for broader validation

Files:

• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If crates/core or crates/adaptive changed, run the full validation matrix across Rust, Python, Go, and Node.js.

Files:

• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

⚙️ CodeRabbit configuration file

crates/{core,adaptive}/**/*.rs: Review the Rust runtime for async correctness, scope isolation, middleware ordering, and event lifecycle regressions.
Pay close attention to task-local/thread-local scope propagation, callback lifetimes, stream finalization, and root_uuid isolation.
Public API changes should preserve existing behavior unless tests and docs show the intended migration path.

Files:

• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/add-binding-feature/SKILL.md)

Implement the new or changed public runtime behavior first in the Rust core, especially under crates/core/src/api/ and related core modules such as crates/core/src/api/runtime/, crates/core/src/codec/, and crates/core/src/json.rs.

Files:

• crates/core/src/api/scope.rs
• crates/core/src/api/llm.rs
• crates/core/src/api/runtime/scope_stack.rs

📄 CodeRabbit inference engine (.agents/skills/add-middleware/SKILL.md)

Wire the new middleware chain into the execute path in crates/core/src/api/tool.rs or crates/core/src/api/llm.rs at the appropriate pipeline stage

Files:

• crates/core/src/api/llm.rs

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

**/*.{md,rst,html,txt}: Always spell NVIDIA in all caps. Do not use Nvidia, nvidia, nVidia, nVIDIA, or NV.
Use an NVIDIA before a noun because the name starts with an 'en' sound.
Do not add a registered trademark symbol after NVIDIA when referring to the company.
Use trademark symbols with product names only when the document type or legal guidance requires them.
Verify official capitalization, spacing, and hyphenation for product names.
Precede NVIDIA product names with NVIDIA on first mention when it is natural and accurate.
Do not rewrite product names for grammar or title-case rules.
Preserve third-party product names according to the owner's spelling.
Include the company name and full model qualifier on first use when it helps identify the model.
Preserve the official capitalization and punctuation of model names.
Use shorter family names only after the full name is established.
Spell out a term on first use and put the acronym in parentheses unless the acronym is widely understood by the intended audience.
Use the acronym on later mentions after it has been defined.
For long documents, reintroduce the full term if readers might lose context.
Form plurals of acronyms with s, not an apostrophe, such as GPUs.
In headings, common acronyms can remain abbreviated. Spell out the term in the first or second sentence of the body.
Common terms such as CPU, GPU, PC, API, and UI usually do not need to be spelled out for developer audiences.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)

Link the first mention of a product name when the destination helps the reader.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

Spell NVIDIA in all caps. Do not use Nvidia, nvidia, or NV.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

**/*.{md,rst}: Format commands, code elements, expressions, package names, file names, and paths as inline code.
Use descriptive link text. Avoid raw URLs and weak anchors such as "here" or "read more."
Use title case consistently for technical documentation headings.
Introduce code blocks, lists, tables, and images with complete sentences.
Write procedures as imperative steps. Keep steps parallel and split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English.
Use can for possibility and reserve may for permission.
Use after for temporal relationships instead of once.
Prefer refer to over see when the wording points readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical docs.
Spell out months in body text, avoid ordinal dates, and use clear time zones.
Spell out whole numbers from zero through nine unless they are technical values, parameters, versions, or UI values.
Use numerals for 10 or greater and include commas in thousands.
Do not add trademark symbols to learning-oriented docs unless the source, platform, or legal guidance explicitly requires them.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-technical-docs.md)

**/*.md: Use title case consistently in technical documentation headings
Avoid quotation marks, ampersands, and exclamation marks in headings
Keep product, event, research, and whitepaper names in their official title case
Use title case for table headers
Do not force social-media sentence case into technical docs
Format code elements, commands, parameters, package names, and expressions in monospace
Format directories, file names, and paths in monospace using backticks
Use angle brackets inside monospace for variables inside paths, such as /home/<username>/.login
Format error messages and strings in quotation marks, keeping literal code strings in code formatting when clearer
Format UI buttons, menus, fields, and labels in bold
Use angle brackets between UI labels for menu paths, such as File > Save As
Use italics for new terms on first use, sparingly and only when introducing the term
Use italics for publication titles
Format keyboard shortcuts in plain text, such as Press Ctrl+Alt+Delete
Use owner/repo link text for GitHub repositories, preferring [NVIDIA/NeMo](link) over prose references like 'the GitHub repo'
Introduce every code block with a complete sentence
Do not make a code block complete the grammar of the previous sentence
Do not continue a sentence after a code block
Use syntax highlighting when the format supports it for code blocks
Avoid the word 'snippet' unless the surrounding docs already use it as a term of art
Keep inline method, function, and class references consistent with nearby docs, omitting empty parentheses for prose readability when no call is shown
Use descriptive anchor text that matches the destination title when possible for links
Avoid raw URLs in running text
Avoid generic anchor text such as 'here,' 'this page,' and 'read more'
Include acronyms in link text when a linked term includes an acronym
Do not link long sentences or multiple sentences
Avoid links that pull readers away from a procedure unless the link is a p...

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (AGENTS.md)

SKILL.md files are skill entrypoints and must start with YAML frontmatter containing at least name and description.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

⚙️ CodeRabbit configuration file

**/SKILL.md: Do not flag SKILL.md files for missing SPDX headers. Skill entrypoints intentionally start with YAML frontmatter instead.
Verify that every SKILL.md keeps valid YAML frontmatter with at least name and description fields before the Markdown body.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• skills/nemo-relay-export-openinference/SKILL.md
• skills/nemo-relay-export-atif-trajectories/SKILL.md

📄 CodeRabbit inference engine (AGENTS.md)

Update README.md, fern/, package READMEs, and binding-support notes when public behavior, package names, examples, or supported bindings change.

**/*.{md,mdx}: Prefer the documented public API, not internal shortcuts
Keep package names, repo references, and build commands current
Keep release-process and release-notes guidance in repo-maintainer docs such as RELEASING.md, not as user-facing docs pages or CHANGELOG.md
Keep stable user-facing wrappers at scripts/ root in docs and examples; only point at namespaced helper paths when documenting internal maintenance work
When detailed dynamic plugin guides exist, keep Rust native plugin examples, Python worker plugin examples, and grpc-v1 protocol details on separate pages

If links in documentation change, run just docs-linkcheck.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• docs/nemo-relay-cli/codex.mdx
• skills/nemo-relay-export-openinference/SKILL.md
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Add the SPDX license header to all Markdown/MDX documentation files using the HTML comment block form.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• docs/nemo-relay-cli/codex.mdx
• skills/nemo-relay-export-openinference/SKILL.md
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

**/*: Format changed files with the language-native formatter before the final lint/test pass.
If dynamic plugin behavior changed, use maintain-dynamic-plugins and include the native SDK, worker protocol, Python SDK, docs, packaging, and Codecov surfaces in the validation plan.
If code changes alter APIs, bindings, commands, paths, packaging behavior, observability/adaptive semantics, or documented best practices, update any dependent maintainer or consumer skills in the same branch.
During iteration, prefer uv run pre-commit run --files <changed files...>.
Before review or handoff, run uv run pre-commit run --all-files.

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• docs/nemo-relay-cli/codex.mdx
• crates/cli/tests/coverage/adapters_tests.rs
• skills/nemo-relay-export-openinference/SKILL.md
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• docs/about-nemo-relay/concepts/events.mdx
• crates/core/src/api/scope.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs

⚙️ CodeRabbit configuration file

**:

AGENTS.md

This file provides guidance to agents, including Claude Code and OpenAI Codex, when working in this repository.

Project Overview

NeMo Relay is a multi-language agent runtime framework for execution scopes, lifecycle events, middleware, plugins, and observability around tool and LLM calls. The core runtime is Rust. Primary supported bindings are Rust, Python, and Node.js. Go and the raw C FFI are experimental and source-first.

The shared runtime model is:

1. Scope stacks decide where work belongs and which scope-local behavior is visible.
2. Middleware registries decide what guardrails and intercepts run around managed calls.
3. Plugins install reusable runtime behavior from configuration.
4. Events record runtime behavior in ATOF form.
5. Subscribers and exporters consume events in-process or export them to ATIF, OpenTelemetry, OpenInference, or other backends.

Repository Structure

The repository layout separates the Rust runtime, language bindings,
documentation, integrations, and agent-facing skills.

crates/
  core/       # Rust core runtime crate, published as nemo-relay
  adaptive/   # Adaptive runtime primitives and plugin components
  python/     # PyO3 native extension for the Python package
  ffi/        # Raw C ABI layer used by downstream bindings such as Go
  node/       # NAPI Node.js binding and JavaScript/TypeScript entry points
python/
  nemo_relay/  # Python wrapper package: scopes, tools, LLM, middleware, typed helpers, plugins, adaptive helpers
  tests/      # Python tests
go/
  nemo_relay/  # Experimental Go CGo binding and tests
fern/         # Fern documentation site
scripts/      # Stable wrappers and helper scripts; build/test/docs entry points live in justfile
skills/       # Published Codex/agent skills for NeMo Relay usage patterns

Prerequisites

Insta...

Files:

• skills/nemo-relay-setup-observability/SKILL.md
• docs/nemo-relay-cli/codex.mdx
• crates/cli/tests/coverage/adapters_tests.rs
• skills/nemo-relay-export-openinference/SKILL.md
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• skills/nemo-relay-export-atif-trajectories/SKILL.md
• docs/about-nemo-relay/concepts/events.mdx
• crates/core/src/api/scope.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/SKILL.md)

MDX top-of-file SPDX comments must use {/* ... */} delimiters instead of HTML comment delimiters (Must-Fix)

In MDX files, top-of-file comments must use JSX comment delimiters ({/* to open and */} to close); do not use HTML comments for MDX SPDX headers

Files:

• docs/nemo-relay-cli/codex.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update docs and examples.

Files:

• docs/nemo-relay-cli/codex.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If documentation examples or commands under docs/ change, run the targeted docs checks appropriate to the change.

Files:

• docs/nemo-relay-cli/codex.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx

⚙️ CodeRabbit configuration file

{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}: Review documentation for technical accuracy against the current API, command correctness, and consistency across language bindings.
Flag stale examples, missing SPDX headers where required, and instructions that no longer match CI or pre-commit behavior.

Files:

• docs/nemo-relay-cli/codex.mdx
• docs/nemo-relay-cli/claude-code.mdx
• docs/configure-plugins/observability/atof.mdx
• docs/nemo-relay-cli/basic-usage.mdx
• docs/instrument-applications/instrument-llm-call.mdx
• docs/about-nemo-relay/concepts/events.mdx

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

**/*.rs: Any Rust change must run just test-rust
Any Rust change must run cargo fmt --all
Any Rust change must run cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all for all FFI work since it is Rust work
Run just test-rust to validate FFI changes
Run cargo clippy --workspace --all-targets -- -D warnings to enforce strict linting on FFI work

When Rust files changed as part of Go work, also run cargo fmt --all, just test-rust, and cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all when Rust files are changed as part of Node work
Run cargo clippy --workspace --all-targets -- -D warnings when Rust files are changed as part of Node work
Run just test-rust when Rust files are changed as part of Node work

When changing the core Rust runtime or Rust-facing API surface, format Rust code with cargo fmt (rustfmt defaults), keep cargo clippy -- -D warnings clean, and satisfy cargo deny check per deny.toml.

**/*.rs: If any Rust code changed, always run just test-rust.
If any Rust code changed, also run cargo fmt --all.
If any Rust code changed, also run cargo clippy --workspace --all-targets -- -D warnings.
For Rust changes headed for review, run cargo fmt --all and cargo clippy --workspace --all-targets -- -D warnings even if relying on pre-commit.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/api/scope.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (AGENTS.md)

Follow binding naming conventions in Rust and Python: use snake_case.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/api/scope.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (AGENTS.md)

**/*.{rs,py,js,mjs,cjs,ts,tsx}: Use Json = serde_json::Value in Rust-facing runtime APIs where the existing code expects JSON payloads.
Use Result<T> with FlowError in core runtime paths, and keep errors explicit and binding-appropriate at the wrapper layer.
Keep async behavior on the existing tokio-based model; bindings should preserve callback and future lifetimes rather than blocking or hiding async work unexpectedly.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/api/scope.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Use language-appropriate naming conventions: Rust snake_case, C FFI exports prefixed nemo_relay_, Go PascalCase, Node.js camelCase, and Python snake_case.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/api/scope.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Add the SPDX license header to all Rust, Go, JavaScript, and TypeScript source files using the corresponding // comment form.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/api/scope.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If a language surface changed, always run that language's test target even when Rust core did not change.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/src/api/scope.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/src/api/runtime/scope_stack.rs
• crates/cli/src/adapters/mod.rs
• crates/core/src/api/llm.rs
• crates/core/tests/unit/llm_api_tests.rs

⚙️ CodeRabbit configuration file

{crates/**/tests/**,python/tests/**,go/nemo_relay/**/*_test.go}: Tests should cover the behavior promised by the changed API surface, including error paths and cross-request isolation where relevant.
Prefer assertions on lifecycle events, scope stacks, middleware ordering, and binding parity over shallow smoke tests.

Files:

• crates/cli/tests/coverage/adapters_tests.rs
• crates/core/tests/unit/context_tests.rs
• crates/core/tests/unit/llm_api_tests.rs